| 1 | # We use `hot-shots` as our DogStatsD client
|
| 2 |
|
| 3 | ## Date
|
| 4 |
|
| 5 | May 18, 2018
|
| 6 |
|
| 7 | ## Contributors
|
| 8 |
|
| 9 | * tzvipm
|
| 10 |
|
| 11 | ## Summary
|
| 12 |
|
| 13 | We use `hot-shots` as our DogStatsD client. It is regularly updated based on `etsy/statsd`, and has a rigorous test suite including performance tests. These characteristics make it stand out compared to alternative solutions.
|
| 14 |
|
| 15 | ## Problem space
|
| 16 |
|
| 17 | We need to submit metrics to DataDog.
|
| 18 |
|
| 19 | ## Solution
|
| 20 |
|
| 21 | We submit metrics to datadog via dogstatsd, based on the [DataDog Developer Documentation](https://docs.datadoghq.com/developers/dogstatsd/):
|
| 22 |
|
| 23 | > The easiest way to get your custom application metrics into Datadog is to send them to DogStatsD, a metrics aggregation service bundled with the Datadog Agent.
|
| 24 |
|
| 25 | This same documentation provides a [list of libraries in various programming languages](https://docs.datadoghq.com/developers/libraries/).
|
| 26 |
|
| 27 | Among those, there are 2 libraries listed under `Node.js` with support for `DogStatsD`:
|
| 28 |
|
| 29 | * `hot-shots`
|
| 30 | * `node-dogstatsd`
|
| 31 |
|
| 32 | `hot-shots` appears to be the clear choice between these 2 for the following reasons:
|
| 33 |
|
| 34 | 1. security - It is actively maintained
|
| 35 | 2. reliability - It has a test suite
|
| 36 | 3. performance - It has performance tests
|